On 1/17/06, <b class="gmail_sendername">DM Smith</b> <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You will notice in our code that we code to interfaces. So there<br>probably should be a BlogEngine interface, perhaps others (e.g. Blog,<br>which defines a site and the user's access to it). We then provide<br>concrete implementations. In this case your code would be derived from
<br>the interface(s). Finally, we use a plug-in model to define a default<br>implementation and alternate implementations (though sometimes we leave<br>the whole alternates until the point that we have a second<br>implementation) When there are alternate implementations, we would
<br>provide options to pick a default from among the implementations.</blockquote><div><br>Ok, good, the blog client library - <a href="https://blogapps.dev.java.net/">https://blogapps.dev.java.net/</a> - I'm using already has these interfaces. I'll look into how you specify implementations.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I would suggest a further abstraction JournalEngine would not presuppose<br>a Web Journal and could be a private local journal. Journal would define
<br>a location for it and the user's access to it. But we can refactor to<br>this when the need arises.</blockquote><div><br>Sure, however I won't be able to work on this for a while, as I'm currently trying to get this site up and running. Would this be a requirement before the code is imported or could we do a phased approach?
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If this is something that should be a user preference as to whether they<br>want to do any blogging, then there should be an option to show or hide
<br>it. If it is something that the user would like to do but might want to<br>show/hide it quickly, then an entry in the view menu is appropriate. And<br>by using a SplitPane, we could hide/show it like we do the Passage Sidebar.
</blockquote><div><br>Yep, and this is already an option, Alt-J IIRC. In addition, the journal is shown using a splitpane so it can be hidden or resized as desired. I do plan to add this option to the config to have it persisted.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This might sound like a lot, but it is pretty easy to do.<br>> #2 - Continue as a separate project, forking code as needed.
<br>><br>> Since Bible Desktop is GPL, the code is available on the<br>> BibleBlogs.Net site [2], so option 1 is more about collaboration.<br>> Option 2 obviously necessitates me finding a new name, but it also
<br>> might help encourage Bible Desktop's design to better accept plugins<br>> and extensions.<br>I think we should move to an OSGI plugin model. I always favor using<br>industry standards.<br>For 2.0 we will probably use RCP from Eclipse. A Blog would then be a
<br>perspective....</blockquote><div><br>There are OSGI implementations for Swing, and in fact, there is a great Swing framework discussion going on right now: <a href="http://www.clientjava.com/blog/2006/01/14/1137282016137.html">
http://www.clientjava.com/blog/2006/01/14/1137282016137.html</a><br><br>My concern about RCP, and I believe this has already been raised, is how it affects WebStart. I'm a big fan of WebStart as we've used it in production applications with good success. I want to try to keep the download as small as possible to encourage folks that aren't necessarily computer savvy and may not have a blazing fast connection. Otherwise, I really like RCP's framework and plugin support and think moving to a flexible platform such as RPC would encourage all kinds of new development.
<br><br>Don<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>> Look forward to your feedback and ideas.<br>><br>> Don
<br>><br>> [1] <a href="http://www.bibleblogs.net">http://www.bibleblogs.net</a><br>> [2] <a href="http://www.bibleblogs.net/study">http://www.bibleblogs.net/study</a><br>> [3] <a href="http://www.rollerweblogger.org/page/project">
http://www.rollerweblogger.org/page/project</a><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> jsword-devel mailing list
<br>> <a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>>
<br>_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote></div><br>