So why should it be in the code? It is sitting there, making the object less portable, whilst adding absolutely nothing to nearly everybody else.
Have you ever used this feature? I bet you haven’t. Somebody once wanted Ini++ to export to CSV. It is automatically portable! The difficulties are hidden from the user, but not put into my code. Then all the features like ‘Merge into other Ini++ object’ and ‘Sort items of groups’ and so forth could be programmed in MMF itself. Maybe just based around a hash-table object which also had some features to do things which would otherwise be slow (sorting and searching for instance). But I don’t have the time or will to work on that, let alone porting the original object.īut imagine this: Suppose the C++ (or whatever) component of Ini++ was very small. The original evolved, but this was designed. I wouldn’t want to anyway: The Ini++ v2.0 object (which to some degree exists, but has never been released) is so much more elegant. There is a lot of code, and a lot of actions. So it should be easy to port it to Java and Flash and iPhone and so forth – but it isn’t. So the Ini++ object really is not a difficult thing. Finally it has a load of actions which could theoretically be programmed yourself such as merging and searching. It also includes other functions, for instance hashing, encryption, debugging dialog boxes and integration with object objects. However, data structures like that are not easy to work with in MMF, and so the object wraps at this up for you. The Ini++ object is fundamentally very simple: It is an associated-array of associated-arrays of strings.
I think this is a great idea, and I think that the Ini++ object is an example of why. When this is out the way I can finally get the Chart object out, which I am really keen to do.Īt the Click Convention, Chris Branch spoke about creating extensions within Multimedia Fusion itself. For instance, saving global strings now works (even if loading global strings does not). Some of the Unicode versions bugs have been fixed, however. I’ve also a request from somebody else to add another feature, and I’ll see if I have to do that. However, the Load Object function was crashing (in either normal or Unicode version of MMF), so I am looking into that, and we’ll have to see what Yves says. Whilst I am here, the latest news with Ini++ is as follows: The undo features are all finished, as mentioned in this post. I didn’t even start programming this, however. I pretty much want to get out of all this MMF programming, at least until MMF3.Īnother idea was a similar editor for editing strings, built around the idea of a jigsaw puzzle style interface where you join things together, and also apply functions to sets of jigsaw puzzles (denoted by a background). However, I am now at the stage of making them editable and I just can’t be bothered anymore. I actually programmed most of this, and I made something which translated MMF expressions to a visual display. This can make expressions a lot easier to read. The final difference is you’d be allowed to introduce variable names and at the bottom you could define them. I thought that perhaps an icon could also have some descriptive text associated with it. Clicking an expression would show a pane at the bottom of the screen with various options. Furthermore, I envisioned a tree on the right where you could drag-and-drop icons from, which would represent expressions. If you typed something like “1/2” it would automatically turn it into a fraction, or you could use buttons like in the first screenshot. I thought it’d be great if Multimedia Fusion had proper equation editor. On the other hand, look at Multimedia Fusions expression editor: These days, Microsoft Word has a really good equation editor built into it:
0 kommentar(er)
