Apidesign at 11:07, 28 October 2013 - 2013-10-28 11:07:53

←Older revision Revision as of 11:07, 28 October 2013
Line 84: Line 84:
--Gustavo 11:59, 23 October 2013 (CEST)
--Gustavo 11:59, 23 October 2013 (CEST)
-
</div>
 
-
== Claire said ... ==
 
-
 
-
<div class='commentBlock'>
 
-
Hi,Making real progress with your Asset Management MP. Really good prcoudt and is proving very useful.We're stuck importing mobile phones. Using this guide and the documents provided, we can add the phone and the number, but do not know how to link them together. We thought it was the IMEI number (FK1), but adding this to the CSV is not playing ball.Do you have any thoughts on this?
 
-
 
-
--Claire 13:11, 23 October 2013 (CEST)
 
-
</div>
 
-
== Sabina said ... ==
 
-
 
-
<div class='commentBlock'>
 
-
Hi,Making real progress with your Asset Management MP. Really good pourdct and is proving very useful.We're stuck importing mobile phones. Using this guide and the documents provided, we can add the phone and the number, but do not know how to link them together. We thought it was the IMEI number (FK1), but adding this to the CSV is not playing ball.Do you have any thoughts on this?
 
-
 
-
--Sabina 13:23, 23 October 2013 (CEST)
 
</div>
</div>

94.23.238.222: Comment provided by Sabina - via ArticleComments extension - 2013-10-23 11:23:14

Comment provided by Sabina - via ArticleComments extension

←Older revision Revision as of 11:23, 23 October 2013
Line 91: Line 91:
--Claire 13:11, 23 October 2013 (CEST)
--Claire 13:11, 23 October 2013 (CEST)
 +
</div>
 +
== Sabina said ... ==
 +
 +
<div class='commentBlock'>
 +
Hi,Making real progress with your Asset Management MP. Really good pourdct and is proving very useful.We're stuck importing mobile phones. Using this guide and the documents provided, we can add the phone and the number, but do not know how to link them together. We thought it was the IMEI number (FK1), but adding this to the CSV is not playing ball.Do you have any thoughts on this?
 +
 +
--Sabina 13:23, 23 October 2013 (CEST)
</div>
</div>

94.23.238.222: Comment provided by Claire - via ArticleComments extension - 2013-10-23 11:11:46

Comment provided by Claire - via ArticleComments extension

←Older revision Revision as of 11:11, 23 October 2013
Line 84: Line 84:
--Gustavo 11:59, 23 October 2013 (CEST)
--Gustavo 11:59, 23 October 2013 (CEST)
 +
</div>
 +
== Claire said ... ==
 +
 +
<div class='commentBlock'>
 +
Hi,Making real progress with your Asset Management MP. Really good prcoudt and is proving very useful.We're stuck importing mobile phones. Using this guide and the documents provided, we can add the phone and the number, but do not know how to link them together. We thought it was the IMEI number (FK1), but adding this to the CSV is not playing ball.Do you have any thoughts on this?
 +
 +
--Claire 13:11, 23 October 2013 (CEST)
</div>
</div>

94.23.238.222: Comment provided by Gustavo - via ArticleComments extension - 2013-10-23 09:59:35

Comment provided by Gustavo - via ArticleComments extension

←Older revision Revision as of 09:59, 23 October 2013
Line 77: Line 77:
--Jimmy 00:15, 22 October 2013 (CEST)
--Jimmy 00:15, 22 October 2013 (CEST)
 +
</div>
 +
== Gustavo said ... ==
 +
 +
<div class='commentBlock'>
 +
First, class specifier neeedd for another reasons (to access NewEnum::NE_One).The reason why your code is working with type specified but without class' keyword is that VS2010 just doesn't support this C++0x (yet)!But VS compiler already had C++ extension to specify types for enumerations similar to proposed in C++0x standard but intended for their clr (layer between C++ and C#) . I get this warning for example:C4480: nonstandard extension used: specifying underlying type for enum enum'An extension to the language under /clr was used without /clr. You can disable C4480 with the warning pragma.
 +
 +
--Gustavo 11:59, 23 October 2013 (CEST)
</div>
</div>

188.143.232.12: Comment provided by Jimmy - via ArticleComments extension - 2013-10-21 22:15:16

Comment provided by Jimmy - via ArticleComments extension

←Older revision Revision as of 22:15, 21 October 2013
Line 70: Line 70:
--Ilker 07:36, 21 October 2013 (CEST)
--Ilker 07:36, 21 October 2013 (CEST)
 +
</div>
 +
== Jimmy said ... ==
 +
 +
<div class='commentBlock'>
 +
The article rdnmies me of the following quote: The first thing they teach you in programming class is the if statement. You then spend your rest of your career trying to avoid it. In the past I have occasionally used similar tactics to those Mark eludes to:private final static Boolean WITH_CACHING = Boolean.TRUE;private final static Boolean WITHOUT_CACHING = Boolean.FALSE;This is obviously not type safe but is very explicit when reading code and means no additional commenting.I think this is equivalent to the enum suggestion ( I guess you'd have to make the Use and DontUse enum implement the same interface though for it to work?)I don't like the idea of passing a map of options because it is not type safe and is quite verbose in both the caller and callee . It's more tempting to fight it using OOAD and DDD. Strategy patterns, fine grain services etc things which will add a certain level of complexity and more classes. I abhor large classes so would rather use these.
 +
 +
--Jimmy 00:15, 22 October 2013 (CEST)
</div>
</div>

94.23.238.222: Comment provided by Ilker - via ArticleComments extension - 2013-10-21 05:36:59

Comment provided by Ilker - via ArticleComments extension

←Older revision Revision as of 05:36, 21 October 2013
Line 63: Line 63:
--Ademir 07:35, 21 October 2013 (CEST)
--Ademir 07:35, 21 October 2013 (CEST)
 +
</div>
 +
== Ilker said ... ==
 +
 +
<div class='commentBlock'>
 +
Do you know, who I can do that in compact fmwreaork?because BinaryFormatter doesn't exist. /// /// Implementacion de la interfaz IClonable. /// Retorna un objeto clonado. public object Clone() { MemoryStream buffer = new MemoryStream(); BinaryFormatter format = new BinaryFormatter(); format.Serialize(buffer, this); buffer.Position = 0; return format.Deserialize(buffer); }
 +
 +
--Ilker 07:36, 21 October 2013 (CEST)
</div>
</div>

94.23.238.222: Comment provided by Ademir - via ArticleComments extension - 2013-10-21 05:35:00

Comment provided by Ademir - via ArticleComments extension

←Older revision Revision as of 05:35, 21 October 2013
Line 56: Line 56:
--Tim Boudreau 18:20, 23 September 2013 (CEST)
--Tim Boudreau 18:20, 23 September 2013 (CEST)
 +
</div>
 +
== Ademir said ... ==
 +
 +
<div class='commentBlock'>
 +
As enums can provide also mehtdos, I think it's better this way:public enum Colors { RED( #ff0000 ), BLUE( #00ff00 ), GREEN( #0000ff ); private String css; private Colors(String css) { this.css = css; } public String toCSS() { return css; }}
 +
 +
--Ademir 07:35, 21 October 2013 (CEST)
</div>
</div>

50.174.70.4: Comment provided by Tim Boudreau - via ArticleComments extension - 2013-09-23 16:20:22

Comment provided by Tim Boudreau - via ArticleComments extension

←Older revision Revision as of 16:20, 23 September 2013
Line 47: Line 47:
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)
 +
</div>
 +
== Tim Boudreau said ... ==
 +
 +
<div class='commentBlock'>
 +
A way around this is to implement an interface on your enums, and code to the interface wherever possible.
 +
 +
If you have code which *really* needs enums, you can use the signature <T extends Foo & Enum<T>> to require one, without specifying the exact type.
 +
 +
--Tim Boudreau 18:20, 23 September 2013 (CEST)
</div>
</div>

JaroslavTulach at 22:15, 16 January 2011 - 2011-01-16 22:15:43

←Older revision Revision as of 22:15, 16 January 2011
Line 12: Line 12:
--stephane.appercel@neuf.fr 16:05, 13 January 2011 (CET)
--stephane.appercel@neuf.fr 16:05, 13 January 2011 (CET)
-
Simple solution except hidden [[API]] catches! Remember the [[enum]] already exists in your [[API]], you cannot define it as ''StandardModuleCategory''! Also ''use the interface everywhere in your code'' - you can't! The whole [[API]] that you have is already using using the old enum, you need to keep it unchanged in order to preserver [[BackwardCompatibility]].
+
Simple solution except hidden [[API]] catches! Remember the [[enum]] already exists in your [[API]], you cannot define it as ''StandardModuleCategory''! You can't just: ''use the interface everywhere in your code''! Your whole [[API]] is already using the old [[enum]], you need to keep it unchanged in order to preserver [[BackwardCompatibility]].
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)

JaroslavTulach at 22:14, 16 January 2011 - 2011-01-16 22:14:39

←Older revision Revision as of 22:14, 16 January 2011
Line 11: Line 11:
--stephane.appercel@neuf.fr 16:05, 13 January 2011 (CET)
--stephane.appercel@neuf.fr 16:05, 13 January 2011 (CET)
 +
 +
Simple solution except hidden [[API]] catches! Remember the [[enum]] already exists in your [[API]], you cannot define it as ''StandardModuleCategory''! Also ''use the interface everywhere in your code'' - you can't! The whole [[API]] that you have is already using using the old enum, you need to keep it unchanged in order to preserver [[BackwardCompatibility]].
 +
 +
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)
 +
</div>
</div>
== Axel said ... ==
== Axel said ... ==
Line 38: Line 43:
--[http://www.dua3.com Axel] 10:44, 15 January 2011 (CET)
--[http://www.dua3.com Axel] 10:44, 15 January 2011 (CET)
 +
 +
Looks like your [[API]] also benefits from the [[Enum]] marker superclass. Otherwise you could not type the first method...
 +
--[[User:JaroslavTulach|JaroslavTulach]] 22:14, 16 January 2011 (UTC)
 +
</div>
</div>