Menu
▾
▴
tmapinet-discuss
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(7) |
Dec
(1) |
|---|
|
From: Marcel H. <mh...@pi...> - 2008-12-16 11:01:38
|
Hi all, I proudly present the first preview release of SharpTM [1]. Today I finished the last lines of code to pass the test cases implemented by the TMAPI.Net project [2]. But beware: the current release is a real early version of the final SharpTM. It is not optimized, without any executable component (just a library), no im- or export functionality, no persistence, ... So there is a lot of work to do. But please give me feedback if you inspect the sources. Kind regards, Marcel [1] http://code.google.com/p/sharptm/ [2] http://sourceforge.net/projects/tmapinet/ |
|
From: Lars H. <he...@se...> - 2008-11-12 16:03:12
|
Hi all,
As announced in the (Java) TMAPI mailing list I added tests for
Topic.remove() and the TopicInUseException.
Your project has already several tests for Topic.remove() but it seems
not to check for
Topic type = tm.createTopic();
Topic topic = tm.createTopic();
topic.addType(type);
type.remove()
C.f.
<http://tmapi.svn.sourceforge.net/viewvc/tmapi/trunk/src/test/java/org/tmapi/core/TestTopicRemovableConstraint.java?view=markup>
line 207 ff
Best regards,
Lars
--
Semagia
<http://www.semagia.com>
|
|
From: Inge H. <ing...@bo...> - 2008-11-07 10:14:34
|
Hi all J Since you do not have an announce mailing list this will have to do... I just wanted to let you know that I am currently implementing TMAPI 2.0 around my TM++ topic maps engine. I am writing it in Managed C++. You can keep track of the development in the CVS here https://sourceforge.net/svn/?group_id=192467 Kind regards, Inge. |
|
From: Stefan K. <ste...@we...> - 2008-11-04 09:28:01
|
Hi Marcel, hi all, > @Stefan, Ralf too: > Lars' request leads to a question: I saw HasFeature method is defined in > ITopicMapSystem and TopicMapSystemFactory in TMAPI.Net. In TMAPI just > TopicMapSystemFactory contains this method. Should we remove the > ITopicMapSystem.HasFeature method to be consistent with TMAPI? > The method "HasFeature()" in ITopicMapSystem must be called "GetFeature()". Fixed this in rev. 62. With kind regards, Stefan |
|
From: Marcel H. <mh...@pi...> - 2008-11-03 22:29:21
|
Hi Lars, > Another issue: You use simple strings as feature names (i.e. line 26). > You should use an IRI here, preferably the already defined feature URI > http://tmapi.org/features/automerge > > [...] Best regards, > Lars I fixed this in rev 59. @Stefan, Ralf too: Lars' request leads to a question: I saw HasFeature method is defined in ITopicMapSystem and TopicMapSystemFactory in TMAPI.Net. In TMAPI just TopicMapSystemFactory contains this method. Should we remove the ITopicMapSystem.HasFeature method to be consistent with TMAPI? Thanks a lot and kind regards, Marcel |
|
From: Marcel H. <mh...@pi...> - 2008-11-03 22:11:36
|
Hi Lars, > Just looked into your SVN and noticed a comment in the > ReifiableTest.cs (line 36). :) > > The test MUST fail if a ModelConstraintException is thrown. If no > exception occurs and the reifier is accepted resp. unchanged, the test > succeed. > > Best regards, > Lars I fixed the test in rev58. Kind regards Marcel |
|
From: Lars H. <he...@se...> - 2008-11-03 19:42:22
|
Hi all, Another issue: You use simple strings as feature names (i.e. line 26). You should use an IRI here, preferably the already defined feature URI http://tmapi.org/features/automerge Strings are too weak. If Alice defines for herself the feature or property "persistent" and Bob uses the same name "property" but Bob assumes completely different semantics of that feature you're stuck. If you use URIs / IRIs for feature names and property names, you can publish a website which describes the feature / property and you'll have a unique identifier for your property / feature (a PSI). Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-11-03 19:26:34
|
Hi all, Just looked into your SVN and noticed a comment in the ReifiableTest.cs (line 36). :) The reason why the same reifier is assigned again is to check if this is accepted by the reifiable construct, c.f. the comment in the Java test case (line 47): <http://tmapi.svn.sourceforge.net/viewvc/tmapi/trunk/src/test/java/org/tmapi/core/TestReified.java?revision=65&view=markup> The test MUST fail if a ModelConstraintException is thrown. If no exception occurs and the reifier is accepted resp. unchanged, the test succeed. Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Marcel H. <mh...@pi...> - 2008-10-29 01:52:35
|
Hi Stefan, as you may mentioned I fixed most of the warnings spit out by CodeAnalysis and StyleCop. At the moment I just receive 85 Warnings. So check out the new revision. To prevent misspelling and layout issues I can recommend the AgentSmith plugin for ReSharper [1]. But you have to configure the rules. You should have a look at your ReSharper formatting options too to match the current code style. As you use Visual Studio too, shouldn't we check in the Visual Studio solution and project files? Tomorrow I'm going to refactor the namespace to TMAPI.Net.Index (TMAPI.Net.Core). Best regards Marcel [1] http://www.agentsmithplugin.com/ |
|
From: Marcel H. <mh...@pi...> - 2008-10-29 01:45:10
|
Hi Stefan and Ralf, do you know what SVN revision of TMAPI was the source of your TMAPI.Net port? Just to get an overview on the changes we have to port in addition from TMAPI to TMAPI.Net. I think it would be much easier to go step by step through the change logs of TMAPI to integrate those into TMAPI.Net. With kind regards, Marcel |
|
From: Stefan K. <ste...@we...> - 2008-10-28 13:39:59
|
Hi Marcel, > [mh] > Writing Org.Tmapi in pascal case is a first step. :-) But in the .NET world > we usually don't use the reverse domain style for namespaces. My > recommendation would be to put the interfaces and classes in the following > structure: > > * TMAPI.Net.Core > - FactoryConfigurationException > - FeatureNotRecognizedException > - FeatureNotSupportedException > - ... > * TMAPI.Net.Index > - IIndex > - ILiteralIndex > - IScopedIndex > - ITypeInstanceIndex > * TMAPI.Net.Core.Tests > - ... > * TMAPI.Net.Index.Tests > - ... > > Of course with this step we are going to distance our self a little bit from > the TMAPI 2.0 Java implementations. But in my opinion we have to look at the > platform specifics and consistencies as well as the TMAPI 2.0 specs. What do > you think about this? > We have a strong Java background and so a lot to learn regarding .Net specific things. Getting closer to the .Net world shouldn't be a problem indeed if it would ease implementation we should take this way. > [mh] > I just did a quick review on your sources. I'm going to check those using > StyleCop [1] and FxCop [2]. I'm curious about the results. 599 warnings. ;-) > But calm down, not all of them are that important. > > I found some referencing issues in the documentation like this: > > /// <summary> > /// Exception thrown when the <see > cref="T:org.tmapi.core.TopicMapsSystemFactory"/> does not > /// recognize the name of a feature that the application is trying > to enable or disable. > /// </summary> > [Serializable] > public class FeatureNotRecognizedException > > The <see>-reference [cref="T:org.tmapi.core.TopicMapsSystemFactory"] does > not point to the correct factory class name (TopicMapSystemFactory without > "s" after TopicMap). Maybe this is the source for the broken CHM help file? > How did you create the CHM? Isn't the generator tool printing out those > wrong reference issues? > Generating the documentation wasn't so straight forward as using JavaDoc ;) During the build process some XML files with the comments are generated. After this we used SandCastle to generate the .chm file. > Just for information: What is your development environment? Do you use some > kind of refactoring tool? > Visual Studio 2008 Professional with Resharper 4.1. With kind regards, Stefan |
|
From: Marcel H. <mh...@pi...> - 2008-10-28 10:51:08
|
Hi Stefan,
>
> Hi Marcel,
>
> at first: Welcome on board :)
>
[mh]
Thanks a lot.
> We're aware of the namespace issue: 'org.tmpai' should be renamed to
> 'Org.Tmapi', right?
>
[mh]
Writing Org.Tmapi in pascal case is a first step. :-) But in the .NET world
we usually don't use the reverse domain style for namespaces. My
recommendation would be to put the interfaces and classes in the following
structure:
* TMAPI.Net.Core
- FactoryConfigurationException
- FeatureNotRecognizedException
- FeatureNotSupportedException
- ...
* TMAPI.Net.Index
- IIndex
- ILiteralIndex
- IScopedIndex
- ITypeInstanceIndex
* TMAPI.Net.Core.Tests
- ...
* TMAPI.Net.Index.Tests
- ...
Of course with this step we are going to distance our self a little bit from
the TMAPI 2.0 Java implementations. But in my opinion we have to look at the
platform specifics and consistencies as well as the TMAPI 2.0 specs. What do
you think about this?
> Are there any other naming issues you stumbled upon?
[mh]
I just did a quick review on your sources. I'm going to check those using
StyleCop [1] and FxCop [2]. I'm curious about the results. 599 warnings. ;-)
But calm down, not all of them are that important.
I found some referencing issues in the documentation like this:
/// <summary>
/// Exception thrown when the <see
cref="T:org.tmapi.core.TopicMapsSystemFactory"/> does not
/// recognize the name of a feature that the application is trying
to enable or disable.
/// </summary>
[Serializable]
public class FeatureNotRecognizedException
The <see>-reference [cref="T:org.tmapi.core.TopicMapsSystemFactory"] does
not point to the correct factory class name (TopicMapSystemFactory without
"s" after TopicMap). Maybe this is the source for the broken CHM help file?
How did you create the CHM? Isn't the generator tool printing out those
wrong reference issues?
Just for information: What is your development environment? Do you use some
kind of refactoring tool?
>
>
> With kind regards,
>
> Stefan
Best regards
Marcel
[1] http://code.msdn.microsoft.com/sourceanalysis
[2] http://blogs.msdn.com/fxcop/
|
|
From: Stefan K. <ste...@we...> - 2008-10-28 10:13:01
|
Hi Marcel, at first: Welcome on board :) We're aware of the namespace issue: 'org.tmpai' should be renamed to 'Org.Tmapi', right? Are there any other naming issues you stumbled upon? With kind regards, Stefan |
|
From: Marcel H. <mh...@pi...> - 2008-10-27 22:51:35
|
Hi Stefan and Ralf, as I told you at TMRA, I would recommend to modify the sources to be consistent with the naming conventions of the MSDN [1]. This is useful to for developers using your sources for other projects. If you want I can fix those naming issues. Best regards Marcel [1] http://msdn.microsoft.com/en-us/library/xzf533w0(VS.71).aspx -- ____________________________________________ Marcel Hoyer Dipl.-Ing. (BA) für Informationstechnik Expert Student Partner (Microsoft Student Program) Microsoft Certified Technology Specialist * .NET Framework 3.5 - Windows Presentation Foundation Applications http://marcelhoyer.de/ ____________________________________________ |
|
From: Marcel H. <mh...@pi...> - 2008-10-27 22:27:19
|
Hi, as already announced in the TMAPI mailing list I created the SharpTM project today at GoogleCode [1]. I'll commit the initial project structure these days. If someone is willing to help out please contact me. Best regards Marcel [1] http://code.google.com/p/sharptm/ -- ____________________________________________ Marcel Hoyer Dipl.-Ing. (BA) für Informationstechnik Expert Student Partner (Microsoft Student Program) Microsoft Certified Technology Specialist * .NET Framework 3.5 - Windows Presentation Foundation Applications http://marcelhoyer.de/ ____________________________________________ |
|
From: Stefan K. <ste...@we...> - 2008-10-27 15:28:16
|
Hi all, the alpha version of TMAPI.Net can be found on sourceforge [1]. TMAPI.Net is a port of the current TMAPAI 2.0 alpha to the C# programming language. By now there is no downloadable package but you can find the documentation and UML diagrams in the wiki [2]. The interfaces and test cases are available through SVN [3]. The test cases are using the xUnit.Net framework [4]. Feel free to checkout the code and have a look at it. For comments and questions you can use TMAPI.Net mailing list [5]. With kind regards, Stefan and Ralf [1] http://sourceforge.net/projects/tmapinet/ [2] http://tmapinet.wiki.sourceforge.net/ [3] http://sourceforge.net/svn/?group_id=240544 [4] http://www.codeplex.com/xunit [5] http://sourceforge.net/mailarchive/forum.php?forum_name=tmapinet-discuss |
|
From: Stefan K. <ste...@we...> - 2008-10-25 16:21:12
|
Welcome to Tmapi.Net mailing list :) ________________________________________________________________________ Schon gehört? Bei WEB.DE gibt' s viele kostenlose Spiele: http://games.entertainment.web.de/de/entertainment/games/free/index.html |
1 message has been excluded from this view by a project administrator.
