KaylaKaze wrote:As for your posts, I'm not sure what to search for. You have over 800 posts so sifting through that would be a pain.
So, since you've presumably been neck deep in the MT code recently and I haven't touched it much since 2007 or so (sadly, it hasn't really changed much since then), what are your thoughts on the difficulty of some of the features I threw out, primarily SQLite3 DB access (like an "executeQuery(db filename, query string)" command) and IRC based "Community" tab? I also had a couple of others I just recently thought of that are seemingly just minor things: loading macro code/HTML from a file (like an "include" to a macro), and making it so you don't select a token if you click on a transparent section of its image?
Here's the most recent, and relevant post about my work. I didn't bother adding it to my sig since something more detailed is coming soon.
I'll be uploading a short demo video soon featuring the SQL features I wrote. The feature's been done for a while now, but we're busy on a lot of stuff these days that it keeps getting relegated to the backburner. It's not on SQLite, however, but on H2, which has several advantages over SQLite that I liked. SQLite is in the mix, however, but used internally, and not accessible to users. IRC is in, that's all I can say for now. It's something we plan to discuss with the community interested in our project to round out the user experience. We don't want to implement all features that won't be used anyway; with that being said, it's functionally finished, but not the final user experience.
Regarding #include-like stuff, indirectly we help by providing several (safe) methods to access the file system, as part of providing alternate methods of managing data beyond the token system. I don't see the added value of creating a system that actually behaves like #include or Java's import, when a proper plug-in system is the target of forks and RPTools. onCampaignLoad should work for most cases, coupled with the new features.
Edit: To what purpose is the click-through transparency for? Not with the current system, and likely not with Swing; whether snapped-to-grid or unsnapped, the bounds are set with regard to each token image. It's just "easier" (I'm just imagining it in my head) with JavaFX. In order to accomplish what I think you want, an image object would need to be aware of either it's transparent or visible areas, and have mouse/touches pass through it if its transparent. Each image would need to be encased in a Node to have this nifty feature, which would be sub-optimal as compared to replicating one image over the Canvas.