Menu
▾
▴
tinytim-discuss — Discussions relating to tinyTiM
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(30) |
May
(4) |
Jun
(19) |
Jul
(36) |
Aug
(21) |
Sep
(10) |
Oct
(18) |
Nov
(43) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(5) |
Feb
(18) |
Mar
(6) |
Apr
|
May
|
Jun
(6) |
Jul
(21) |
Aug
(47) |
Sep
(3) |
Oct
|
Nov
(5) |
Dec
|
| 2010 |
Jan
(8) |
Feb
|
Mar
(5) |
Apr
(2) |
May
|
Jun
(14) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
(4) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|
From: Stefan L. <li...@go...> - 2008-06-27 15:31:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Lars, Ich hoffe ich habe mit meiner provokationsmail auf topicmapmail keine zu schlechte laune gemacht, aber ich seh dich seit wochen überall ordentlich posten und ews scheint nichts zurückzukommen. zu dem sl4j, klar facaden sind immer gut, hätte nur ein bedenken für die leute die bisher tinyTIM in Applets benutzt haben, die müssen nur die logging jars mit reinpacken. kriegen wir es nicht clever hin, das logging pluggable zu halten, so dass man es auch ohne logging betreiben kann. Wer es mit haben möchte, der kann ja gerne die beiden jars reinpacken was meinste? Lars Heuer wrote: > Hi Stefan, > > [Using Java Logging] >> I totally agree, we should keep it as simple as possible without any >> additional jars. > >> as a programmer i'm only used to log4j, so i don't know much about >> the java logging api and its pros and cons. > > Markus Ueberall suggested to move to SLF4J <http://www.slf4j.org/>. > Through this facade nearly all logging frameworks are supported > (commons logging, log4j, ...). > > If we'd move to SLF4J the user can use her favourite logging framework > by adding the particular lib to the class path. > > AFAIK, tinyTiM itself does not use any logging (yet). The CXTM > serializer uses logging. > > If we use SLF4J, we need two small jars (the SLF4J API and one of the > implementations, i.e. the one which uses Java logging). > > What do you think? > > Best regards, > Lars -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIZQapbsixtqnWg1oRAtP0AJ4hOOe8fTucXpHPHAdOP3gnYRAhegCfS9ad F+cmrn143fHHzjtHhDgfPGc= =Qsgr -----END PGP SIGNATURE----- |
|
From: Lars H. <he...@se...> - 2008-06-27 15:15:05
|
Hi Stefan, [Using Java Logging] > I totally agree, we should keep it as simple as possible without any > additional jars. > as a programmer i'm only used to log4j, so i don't know much about > the java logging api and its pros and cons. Markus Ueberall suggested to move to SLF4J <http://www.slf4j.org/>. Through this facade nearly all logging frameworks are supported (commons logging, log4j, ...). If we'd move to SLF4J the user can use her favourite logging framework by adding the particular lib to the class path. AFAIK, tinyTiM itself does not use any logging (yet). The CXTM serializer uses logging. If we use SLF4J, we need two small jars (the SLF4J API and one of the implementations, i.e. the one which uses Java logging). What do you think? Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-06-02 14:19:43
|
Hi Stefan, I like to release a new tinyTiM Version, do you mind if we enter the Beta phase now? Before we do the final release I like to work a bit on the Locator implementation (see <http://sourceforge.net/tracker/index.php?func=detail&aid=1979396&group_id=102341&atid=631667>). If someone else want to work on it, I wouldn't mind. ;) Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-05-19 13:48:01
|
Hi all, The tinyTiM project proudly announces the availability of a new release of the CXTM serializer for tinyTiM. The serializer implements the current CXTM ballot draft (dtd. 2008-05-15) now, see <http://www.isotopicmaps.org/cxtm/> for details. You can download it from the project page of tinyTiM: <http://sourceforge.net/projects/tinytim> <http://sourceforge.net/project/showfiles.php?group_id=102341&package_id=115215&release_id=600331> What is tinyTiM - CXTM? ----------------------- tinyTiM is a tiny Topic Maps engine which keeps topic maps in-memory. This Topic Maps engine is meant to be used together with the TMAPI interfaces, see <http://www.tmapi.org/> for details. The CXTM subpackage provides the serialization of topic maps into Canonical XTM (CXTM) <http://www.isotopicmaps.org/cxtm/>. Feedback is welcome! Best regards, Lars and the tinyTiM project Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-05-08 12:42:55
|
Hi all, Sorry for the various announcements, but there happens a lot around tinyTiM. ;) This is the last announce this week. The tinyTiM project proudly announces the availability of the first release for XTM 1.0/2.0 support for tinyTiM. You can download it from tinyTiM's project page <http://sourceforge.net/projects/tinytim> <http://sourceforge.net/project/showfiles.php?group_id=102341&package_id=109878&release_id=597992> What is tinyTiM - I/O? ---------------------- tinyTiM is a tiny Topic Maps engine which keeps topic maps in-memory. This Topic Maps engine is meant to be used together with the TMAPI interfaces, see <http://www.tmapi.org/> for details. The I/O package provides an API to import serialized topic maps. It depends on Semagia MIO which provides a streaming Topic Maps API implementation. Currently, only XTM 1.0 and 2.0 is supported. Feedback is welcome! :) Best regards, Lars and the tinyTiM project -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-05-07 22:00:57
|
Hi all, The tinyTiM project proudly announces the availability of the first release of the CXTM serializer for tinyTiM. The serializer supports the current CXTM draft dtd. 14.04.2008, see <http://www.isotopicmaps.org/cxtm/2008-04-14/> for details. You can download it from the tinyTiM's project page <http://sourceforge.net/projects/tinytim> <https://sourceforge.net/project/showfiles.php?group_id=102341&package_id=115215&release_id=597873> Note: You need tinyTiM 1.5.0 alpha2 to use the tinyTiM CXTM package! What is tinyTiM - CXTM? ----------------------- tinyTiM is a tiny Topic Maps engine which keeps topic maps in-memory. This Topic Maps engine is meant to be used together with the TMAPI interfaces, see <http://www.tmapi.org/> for details. The CXTM subpackage provides the serialization of topic maps into Canonical XTM (CXTM) <http://www.isotopicmaps.org/cxtm/>. Feedback is welcome! :) Best regards, Lars and the tinyTiM project -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-05-05 13:04:11
|
Hi all, The tinyTiM project proudly announces the availability of a new release of the tinyTiM Topic Maps engine. This release contains a few bugfixes and some utility classes were added. Further a 'vocabulary' package was added which provides access to commonly used PSIs (TMDM / XTM 1.0). You can download it from the tinyTiM's project page <http://sourceforge.net/projects/tinytim> <https://sourceforge.net/project/showfiles.php?group_id=102341&package_id=131212&release_id=597156> What is tinyTiM? ---------------- tinyTiM is a tiny Topic Maps engine which keeps topic maps in-memory. This Topic Maps engine is meant to be used together with the TMAPI interfaces, see <http://www.tmapi.org/> for details. Feedback is welcome! :) Best regards, Lars and the tinyTiM project -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-25 21:13:18
|
Hi all, The tinyTiM project proudly announces the availability of new release of the tinyTiM Topic Maps engine. The engine was rewritten from scratch and requires Java 1.5. If you need a small, TMAPI compatible in-memory Topic Maps engine, give it a try! :) You can download it from the tinyTiM's project page <http://sourceforge.net/projects/tinytim> <http://sourceforge.net/project/showfiles.php?group_id=102341&package_id=131212&release_id=594984> It lacks of documentation, but if you're familiar with TMAPI, you can use tinyTiM without any problem. For an introduction into TMAPI see the article from Java enthusiast Robert Barta <http://www.xml.com/pub/a/2005/02/02/tmapi.html> and the TMAPI developers guide <http://tmapi.org/guide/index.html> Feedback is welcome! :) Best regards, Lars and the tinyTiM project -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-25 20:40:26
|
Hi Stefan, [...] > what do you think about a persistent layer to tinytim 1.5/2.0 This is an interesting idea. But I am afraid that it would complicate tinyTiM since we'll have to provide transactions and so on. tinyTiM wouldn't be sooo tiny then. ;) What I personally like about tinyTiM is, that it sooo easy to deploy. Just add a few libs and you have a TMAPI compatible Topic Maps engine. It would be great if we could make the backend plugable. I am not sure if that is possible. On the other hand, we have TM4J as Open Source Topic Maps engine which supports persistent topic maps. And it seems that TM4J will be developed further in the very near future. Xuân has already developed a TMDM compatible version (it seems to support JDO, not sure). Having said that, a persistent backend has currently no high priority for me, but we should consider it. Best regards, Lars -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-25 20:17:07
|
Hi Stefan, Sorry, I've had some problems with my Internet connection. [...] > Why you do you multiply the events with the EventMultiplier? If you look again into it, it has been simplified. Now, I just create additional ADD_<child> events if a parent Topic Maps construct (topic or association) is added. > I think if you remove an Associtation the Event.REMOVE_ROLE event is > fired two times, first at the eventMultiplier on > Event.REMOVE_ASSOCIATION and then again on AssocitationRole.remove() No, Asscociation.remove() just sends a simple REMOVE_ASSOCIATION event, the EventMultiplier adds the missing REMOVE_ROLE events. The event system is a bit fragile currently. The event multiplier sends now less events because it has caused trouble already. This is fixed. Maybe we can overwork it through the next releases. Best regards, Lars -- http://www.semagia.com |
|
From: Stefan L. <li...@ap...> - 2008-04-25 17:21:43
|
Hi Lars, as i went through tinyTIM 1.5 i saw that you are using a pluggable Java Collection Framework (java/trove for now). I remembered some project that was building a persisten JCF with a JDBC backend. I did not found it directly but some similar stuff e.g. the berkeleyDB JE [1] so maybe think about this easy way to persist tinyTIM in the future or lets extend tinyTIM using JPOX or hibernate what do you think about a persistent layer to tinytim 1.5/2.0 Stefan [1]http://www.oracle.com/technology/documentation/berkeley-db/je/collections/tutorial/intro.html |
|
From: Stefan L. <li...@ap...> - 2008-04-25 16:41:45
|
Hi Lars, first of all great great work, i took a first deep look into your implementation and the event API catched my eye. Today i don't develop new stuff without such an event based system underneath. Its great for enhancement later in the process. One questions: Why you do you multiply the events with the EventMultiplier? I think if you remove an Associtation the Event.REMOVE_ROLE event is fired two times, first at the eventMultiplier on Event.REMOVE_ASSOCIATION and then again on AssocitationRole.remove() Or did i missed a point? Again great work, Stefan Lars Heuer wrote: > Hi, > > Finally, the SVN contains a complete Topic Maps engine ;) > > A bit rough at some edges, but everything works. > > The code passes all tmapi.core / tmapi.index tests plus the tests in > the SVN. > > Tonight / tomorrow morning I'll finish the CopyUtils class which is > responsible for merging topic maps and provide a build.xml file. > > I think we can release an alpha version, then? > > Best regards, > Lars |
|
From: Lars H. <he...@se...> - 2008-04-24 15:43:45
|
Hi Stefan, > +1 > i'll have a look at the release on the weekend Great! :) I'll prepare everything. :) Best regards, Lars -- http://www.semagia.com |
|
From: Stefan L. <li...@ap...> - 2008-04-24 15:11:13
|
+1 i'll have a look at the release on the weekend Lars Heuer wrote: > [...] >> should release 1.5alpha. Is that okay? "alpha" does not imply that >> everything works. We can release it, hope for feedback and work >> further in the trunk. I have some more utility classes which I like to > [...] > > Okay, if nobody objects, I'll prepare a release. :) > > Best regards, > Lars |
|
From: Lars H. <he...@se...> - 2008-04-24 14:40:32
|
[...] > should release 1.5alpha. Is that okay? "alpha" does not imply that > everything works. We can release it, hope for feedback and work > further in the trunk. I have some more utility classes which I like to [...] Okay, if nobody objects, I'll prepare a release. :) Best regards, Lars -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-24 12:49:23
|
Hi, I added some more tests, completed the CopyUtils class (tests are missing, though) and changed something here and there. I'll prepare some more tests and if everything works as expected, we should release 1.5alpha. Is that okay? "alpha" does not imply that everything works. We can release it, hope for feedback and work further in the trunk. I have some more utility classes which I like to have in the final release, i.e. one that removes duplicates from several Topic Maps constructs. Best regards, Lars -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-23 17:34:41
|
Hi, Here a short overview what has changed from 1.0 to the current SVN version: - Automerge is not supported anymore Reason: tinyTiM does not ensure that the topic references are kept valid. We'd have to use a mechanism like TM4J where the merged topics reference to each other. This is more work than necessary, I think. - Merging works (at least it should ;)) Merging does suppress duplicates and ensures that all topic characteristics are transferred from one topic to the other. (Topic map merging does not work yet, but should tomorrow) The new merging mechanism bypasses TMAPI and works on top of tinyTiM's own API which should result in a faster merging process - Two non-TMAPI indexes: TypeInstanceIndex and ScopedIndex. These are used while merging and they have a simplified API compared to the quite heavy TMAPI index API - Introduced interfaces IReifiable, ITyped etc. These interfaces simplify access to TMDM features. I think we should remove these if we move to TMAPI 2.0 - Configurable collection factory It's possible to replace the collection factory (factory used to create all Maps / Sets in the core) with a custom implementation. Currently, tinyTiM supports a TroveCollectionFactory (if Trove4J is found in the class path) and a standard JavaCollectionFactory which uses the standard Java Collections. - Some kind of event API Well, this is not meant to be utilised by 3rd parties and needs more work, I guess. - Java 1.5 (where possible since TMAPI is not 1.5-aware) Best regards, Lars -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-23 16:22:43
|
Hi, Finally, the SVN contains a complete Topic Maps engine ;) A bit rough at some edges, but everything works. The code passes all tmapi.core / tmapi.index tests plus the tests in the SVN. Tonight / tomorrow morning I'll finish the CopyUtils class which is responsible for merging topic maps and provide a build.xml file. I think we can release an alpha version, then? Best regards, Lars -- http://www.semagia.com |
|
From: Lars H. <he...@se...> - 2008-04-23 11:22:57
|
[...] > It's not ready, though. Within the next hours, I'll commit more. The [...] That's also the reason why I made no announcement :) I'll inform you once the code is complete. Best regards, Lars |
|
From: Lars H. <he...@se...> - 2008-04-23 10:57:50
|
Hi Stefan, > you already commited your stuff? Yes, since last weekend I commit stuff. ;) It's not ready, though. Within the next hours, I'll commit more. The core is ready, the index stuff is incomplete. But I hope, that I have a complete version this evening. Best regards, Lars |
|
From: Stefan L. <li...@ap...> - 2008-04-23 07:18:18
|
+1 on 1.5 you already commited your stuff? Lars Heuer wrote: > Hi Stefan, > >> Just to make a clean decission on which Java Version tinyTIM 1.5 >> will rely: > > The code in the SVN relies on 1.5. It might be possible that we can > support 1.4 via Retroweaver, though. But I wouldn't offer a 1.4 > version until someone needs it. IMO our audience has moved to 1.5. > > Best regards, > Lars |
|
From: Lars H. <he...@se...> - 2008-04-22 15:40:33
|
Hi Stefan, > Just to make a clean decission on which Java Version tinyTIM 1.5 > will rely: The code in the SVN relies on 1.5. It might be possible that we can support 1.4 via Retroweaver, though. But I wouldn't offer a 1.4 version until someone needs it. IMO our audience has moved to 1.5. Best regards, Lars -- http://www.semagia.com |
|
From: Stefan L. <li...@ap...> - 2008-04-22 15:10:03
|
Hi, Just to make a clean decission on which Java Version tinyTIM 1.5 will rely: [ ] 1.4 [ ] 1.5 [ ] 6 |
|
From: Stefan L. <li...@ap...> - 2008-04-22 15:08:10
|
Hi, I totally agree, we should keep it as simple as possible without any additional jars. as a programmer i'm only used to log4j, so i don't know much about the java logging api and its pros and cons. stefan Lars Heuer wrote: > Hi, > > I wonder which logging framework we should use for tinyTiM. Maybe we > should use the Java Logging API? It would support the tinyTiM motto > "Just download and use it" without the need to install other jars. > > Personally, I like SLF4J <http://www.slf4j.org/> which supports the > Java 1.4 logging framework. But this would require one additional lib > in the classpath. > > In conclusion, I think we should stick with the standard Java Logging > API. > > Thoughts? > > Best regards, > Lars |
|
From: Lars H. <he...@se...> - 2008-04-22 14:49:58
|
Hi, I wonder which logging framework we should use for tinyTiM. Maybe we should use the Java Logging API? It would support the tinyTiM motto "Just download and use it" without the need to install other jars. Personally, I like SLF4J <http://www.slf4j.org/> which supports the Java 1.4 logging framework. But this would require one additional lib in the classpath. In conclusion, I think we should stick with the standard Java Logging API. Thoughts? Best regards, Lars -- http://www.semagia.com |
7 messages has been excluded from this view by a project administrator.
